Concept Link IconServiceXG Basics

Bringing it all together—WriterXG technology

It's not necessary to understand WriterXG's development language or architecture, but a high-level system component introduction could be helpful as you administrator the configuration and security.

Ecrion Omni System (EOS)

Template publishers use EOS, a web portal and development environment, to house the templates, work flows, and publishing software. This is where the templates are created and edited. An API keyClosed An application programming interface key (API key) is a code passed by computer programs calling an application programming interface (API) to identify the program and the user to the Web site or application. allows the basys application to ‘talk’ to the EOS publishing web portal and ensures the templates are up-to-date and the data displays where it should. See Add or verify the WriterXG API key for more information.

XML

XML or eXtensible Markup Language is the ‘language’ of the template's data. XML is basically information wrapped in tags <>. It’s similar to HTML—HyperText Markup Language. Unlike HTML, with XML the author has the freedom to create self-explanatory elements as needed. At a high-level an XML document contains elements, element attributes and values, and data. To view XML data elements in a WriterXG template, see View a template's XML elements.

ServiceXG system processes and the templates

The template benefits go beyond formatting and flexibility, incorporating the basys business process data really makes them valuable. This is done by linking the basys processes or function data with the best practice templates (see samples of the Best practice templates). The processes are already setup for you, but you'll need to link the processes to the templates based on your processes. See Process to template links for more information.

Security

The same security that applies in ServiceXG applies to WriterXG documents. For example, if an operator doesn’t have access to a session or a fund in ServiceXG the same applies to WriterXG. See Fund Control for more information.

  • You can add Template—Fund level security in the Template Configuration window for templates that must be secured at the fund level. See Configure a templatefor more information.
  • Additional security within the Ecrion Omni System is administered by basys that restricts access to templates and configuration or publishing features.
  • If you have a document management system and use a review and approval process for select documents, you’ll need to set an additional layer of security. See Manage the WriterXG document approval process permissions.

Concept Link IconSEE ALSO